Hi Our Exchange 2007 domain is currently company.com. One of our business units is splitting off and joining a sister company, although they will still be located on our premises. Effectively, this means that their mailboxes will be located at partner.com (Exchange 2007 too) but they will logging onto PC's in company.com So the plan is i. Log onto PC in company.com ii. Using a secondary logon, access their mailboxes via Outlook 2007 in the partner.com domain Network connectivity is not an issue etc. BUT - when testing, what we've noticed is that these users can't access OOF and Availability service. Seems like they can't access the relevant URL's because Autodiscover is not working. There is actual connectivity to these URL's. I believe this is something to do with an SCP record for the Autodiscover service for Partner.com not being in our AD environment? Does anyone know what our solutions are? The more straightforward the better :-)

i am guessing you are able to access autodiscoverer.partner.com url from cliets and ports are open. does this oof work if it is joined to partner.com domain , this test will tell us, if this is issue with connectivy or exchange configuration or AD issues due to different domain tell me the results To Run the Test e-mail Auto Configuration test: Press and hold the CTRL key and then right-click the Outlook icon in the system tray. Click Test e-mail Auto Configuration. In the E-mail Address box, type the alias of the affected user. In the Password box, type the user’s password. Click to select the Use Autodiscover check box, and then click Test. Back to the top Thanks Uday Kiran, Senior Consultant Cyquent Technology Consultants, Dubai Please Mark as answer if it helps you

Hi If I run the Test Email Autoconfiguration, I get nothing, not even the email address is pre-populated to carry out the test.

Hi Our Exchange 2007 domain is currently company.com. One of our business units is splitting off and joining a sister company, although they will still be located on our premises. Effectively, this means that their mailboxes will be located at partner.com (Exchange 2007 too) but they will logging onto PC's in company.com So the plan is i. Log onto PC in company.com ii. Using a secondary logon, access their mailboxes via Outlook 2007 in the partner.com domain Network connectivity is not an issue etc. BUT - when testing, what we've noticed is that these users can't access OOF and Availability service. Seems like they can't access the relevant URL's because Autodiscover is not working. There is actual connectivity to these URL's. I believe this is something to do with an SCP record for the Autodiscover service for Partner.com not being in our AD environment? Does anyone know what our solutions are? The more straightforward the better :-) There are two resolution for OOF and free/busy issue for users in partner.com: 1. Use Outlook Anywhere for users in partner.com, so that they can access Autodiscover service and Availability service via external DNS. It is easy to deploy. For more information, please refer to the following Microsoft article: Deploying Outlook Anywhere http://technet.microsoft.com/en-us/library/aa998934(EXCHG.80).aspx Use Outlook Anywhere to connect to your Exchange server without VPN http://office.microsoft.com/en-us/outlook-help/use-outlook-anywhere-to-connect-to-your-exchange-server-without-vpn-HP010102444.aspx 2. Deploy cross forests free/busy information access. It can be complicated. You need to sync GALs first, setup the autodiscover cross forests access and then the availability cross forests access. For more information, please refer to the following Microsoft articles: How to Configure the Availability Service for Cross-Forest Topologies http://blogs.technet.com/b/exchange/archive/2011/03/04/3412075.aspx. Configure the Availability Service for Cross-Forest Topologies http://technet.microsoft.com/en-us/library/bb125182.aspx Best regards, Fiona Liao Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi If I run the Test Email Autoconfiguration, I get nothing, not even the email address is pre-populated to carry out the test. This is because the current logging user account is company.com which does not contain a coresponding mailbox. Even though you type the email address manually, the Test will be failed since there is no any parnet.comrelated record in company.com. -Fiona Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

You need to use XML Redirection. Done this with Outlook Anywhere and linked mailboxes in large scale projects. This will make Autodiscover fully operational, with OOF, Availability, download of the OAB and you can do the Autodiscover test in Outlook. (1) Create a folder and name it C:\Auto (2) Copy the file Autodiscover.xml to it (for details, see below) (3) Reference this XML file in the registry The Autodiscover file You must change the value mail.domain.com ------------------------------- autodiscover.xml --------------------- <?xml version="1.0" encoding="utf-8"?> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <Account> <AccountType>email</AccountType> <Action>redirectUrl</Action> <RedirectUrl>https://mail.domain.com/autodiscover/autodiscover.xml</RedirectUrl> </Account> </Response> </Autodiscover> ------------------------------- autodiscover.xml ---------------------- The Registry entry You must change domain.com to the valid SMTP address extension –––––––––– autodiscover.reg –––––- [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover] "domain.com"="c:\\auto\\autodiscover.xml" "PreferLocalXML"=dword:00000001 –––––––––– autodiscover.reg –––––- Outlook 2007: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover Outlook 2010: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover MCTS: Messaging | MCSE: S+M

P.S. You can make this solution even more robust by adding these registry entries: "ExcludeScpLookup"=dword:00000001 "ExcludeHttpsAutodiscoverDomain"=dword:00000001 "ExcludeHttpsRootDomain"=dword:00000001 "ExcludeSrvLookup"=dword:00000001 "ExcludeHttpRedirect"=dword:00000000 "ExcludeSrvRecord"=dword:00000001 For more information see here: Potential Autodiscover Issue During E-Mail Coexistence http://social.technet.microsoft.com/Forums/en-US/onlineservicesmigrationandcoexistence/thread/d6c69c69-6524-493b-a0c6-21c79e146ce7/ Outlook 2007 unexpectedly connects to an on-premise Exchange Server 2007 server mailbox instead of an Exchange Online server mailbox http://support.microsoft.com/kb/956297/en-us MCTS: Messaging | MCSE: S+M

Just some comments (didn't have so much time earlier today): What I called domain, should be partner.com. So you need to adjust the redirect statement to RedirectUrl>https://mail.partner.com/autodiscover/autodiscover.xml</RedirectUrl> And the registry entry to "partner.com"="c:\\auto\\autodiscover.xml" So how does this work? All Outlook clients are members of the domain company.com. They will by default examine if there is a Service Connection Point (SCP) in company.com. There is, but for those who need to access the mailboxes in partner.com, they don't get any correct information. Even worse, they will do an Autodiscover attempt: * Every time on startup * Every 60 minutes * Every time when there is a connection error. So, as a consequence, OOF, OAB and Availability with free / busy will not work, because no valid URLs are provided. With XML redirection, we state PreferLocalXML. This means, check is there is an XML redirection. This redirection will work for everybody that has @partner.com in their primary SMTP address. Now they will be redirected to the partner.com URI, in this example assuming this is https://mail.partner.com/autodiscover/autodiscover.xml. Note, this redirection is applied on a user-per-user basis, in HKCU. You can do the Autodiscover test now and see that you are getting the correct partner.com URLs. Do also take a look at the log tab. If you want single sign-on for these clients (no need to type in their password), you could make their mailboxes linked mailboxes in partner.com and use this method to provide the correct URLs. This requires as a minimum a one-way external trust. partner.com must trust company.com. The clients have their active logon account in company.com and an associated disabled account in partner.com with a mailbox. This disabled account can also be used for OCS / Lync and SharePoint with single sign-on. We do all that with some 60-70 users on a permanent basis. MCTS: Messaging | MCSE: S+M

Thanks everyone for their input on this. Jon: Couple of questions on your suggestion i. Does Outlook Anywhere need to be enabled on our CAS boxes for this to work? ii. "All Outlook clients are members of the domain company.com. They will by default examine if there is a Service Connection Point (SCP) in company.com. There is, but for those who need to access the mailboxes in partner.com, they don't get any correct information" Can we add an Service Connection point within domain.com for company.com, if that makes any sense?

(1) No, not necessary with Outlook Anywhere on company.com. (2) No, you cannot add another SCP. Just follow the steps described above for one client, and you should see that it works. You must edit the XML file for your purpose and the registry entry that point to it.MCTS: Messaging | MCSE: S+M

Thanks everyone for the answers.Marketing Forum | Webmaster Pride | Webmaster Forum

Thanks everyone for their input on this. Jon: Couple of questions on your suggestion i. Does Outlook Anywhere need to be enabled on our CAS boxes for this to work? ii. "All Outlook clients are members of the domain company.com. They will by default examine if there is a Service Connection Point (SCP) in company.com. There is, but for those who need to access the mailboxes in partner.com, they don't get any correct information" Can we add an Service Connection point within domain.com for company.com, if that makes any sense? 1. Outlook Anywhere must be enabled on the CAS server in partnet.com. 2. No, you can't. the SCP record can only be imported between two trusted foreasts. BTW, the third resolution for your original questions is using Linked mailbox if you have Exchange server in company.com. It should be the most easy method to deployment. For more, see http://technet.microsoft.com/en-us/library/bb123524(EXCHG.80).aspx. -Fiona. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.